Release 10.1A: OpenEdge Development:
Progress Dynamics Advanced Development

Naming conventions for UI events and custom super procedures

There is a reason for the form of the name CreditLimitLeave. The Migration utility converts static viewers to dynamic ones. In doing this, it not only creates all the appropriate Repository data to register the viewer and to represent its fields and all of their attributes, but it also strips any custom code from the static viewer and writes it to a custom super procedure. Any trigger code defined for user interface events is placed into internal procedures using the naming convention of <WidgetName><EventName>. Hence a UI trigger that is defined ON LEAVE OF CreditLimit in a static viewer will cause the Migration utility to generate an internal procedure called CreditLimitLeave with the same code in it, and place this into the custom super procedure for the viewer. There is no absolute need for you to use the same naming convention, since if you follow the guidelines of this chapter, you will be creating super procedures for your static viewers yourself, so that there will be no code left for the Migration utility to convert. Nonetheless, if you follow this naming convention in creating procedures in your custom super procedures, your code will be consistent with what the Migration utility does for static procedures that need converting.

Obviously, the code the Migration utility strips out of existing viewers and puts into a super procedure is not likely to compile or run correctly without modification, because of the issues discussed in this chapter. The intention is simply to salvage the existing code and move it to a place where the developer can then edit it as necessary to make it work in the context of a super procedure.

In addition, the Migration utility creates a default super procedure for each converted static object that has the base table name of the SDO for the object plus the extension super.p. So in this case, if you call your super procedure customersuper.p, it will match the naming convention used for converted objects.